Blog

Brad Wood

July 05, 2013

Spread the word


Share your thoughts

If you're using external Jar files in your project, you may be loading them at run time with Mark Mandel's JavaLoader project.  (CF10 allows for dynamic loading of Jar files, but for people still on CF8, or 9, JavaLoader is the defacto method)
If you're manually creating and using the JavaLoader CFC, please remember that WireBox has a dedicated "JavaLoader" namespace in its mapping DSL to handle this for you using ColdBox's JavaLoader Plugin.  Here all you have to do:

Put a javaloader_libpath setting in your config file that tells ColdBox where the your Jars are:

ColdBox.cfc
// custom settings
settings = {
    javaloader_libpath = "/includes/jars/"
};

If you have more than one Jar directory, simply pass in a comma-delimited list, OR an array of paths.  Your choice.

Now you can inject that class into your components by using the "javaloader" namespace and following it by the Java classpath:

component {
    property name="UASparser" inject="javaLoader:cz.mallat.uasparser.UASparser";
}

That will inject the Java Class definition (which is fine for static classes).  If you need an instance, you'll want to call the init() method to actually instantiate it.

function onDIComplete() {
    oUASparser = UASparser.init(ExpandPath("/includes/uas.ini"));
}

That's not the only way-- this one-liner accomplishes the same thing:

oUASparser = getModel(dsl="javaloader:cz.mallat.uasparser.UASparser").init(ExpandPath("/includes/uas.ini"));

More info here: http://wiki.coldbox.org/wiki/Plugins:JavaLoader.cfm
And here: http://wiki.coldbox.org/wiki/WireBox.cfm#ColdBox_Namespace

Add Your Comment

(2)

Dec 09, 2014 10:39:20 UTC

by Daniel

How to add javaloader_libpath in wirebox standalone..?

Dec 09, 2014 12:11:15 UTC

by Brad Wood

The "javaloader" DSL namespace is only available in WireBox when it is linked to ColdBox. That's because it depends on the JavaLoader Plugin which is part of ColdBox. Note: in ColdBox 4, JavaLoader has been removed from the ColdBox core and is an optional module called cbjavaloader. So you can't use the DSL I showed in this post by default, HOWEVER you can add this into WireBox standalone if you wish. Look at how the cbjavaloader module works-- it registers the "javaloader" DSL on the fly. https://github.com/ColdBox/cbox-javaloader/blob/master/modules/cbjavaloader/ModuleConfig.cfc#L26 You could probably make a standalone version of cbjavaloader that reused the same loader object and registered the DSL. Honestly though, i would save my time and just start using ColdBox :) Using JavaLoader in ColdBox 4 is as simple as this: CommandBox> install cbjavaloader Done!

Recent Entries

BoxLang AI: The Foundation for Real-World AI Systems!

BoxLang AI: The Foundation for Real-World AI Systems!

BoxLang AI: From AI Experiments to Real-World Systems!

Why we built BoxLang AI?

AI is everywhere. New models, new tools, new announcements every week. But for most teams, the real challenge isn’t choosing ...

Victor Campos
Victor Campos
January 30, 2026
Speaker Featuring - Round 1

Speaker Featuring - Round 1

Every conference is more than the talks we see on stage it’s also the story of the people who make it possible.

With the first round of Into the Box 2026 sessions and workshops now live, we’re excited to introduce some of the speakers who will be joining us this year. These community members, practitioners, and Ortus team experts bring decades of real-world experience across CFML, BoxLang, JVM modernization, testing, AI, and cloud-native development.

Victor Campos
Victor Campos
January 26, 2026
First Round of the Into the Box 2026 Agenda Is Live

First Round of the Into the Box 2026 Agenda Is Live

Into the Box 2026 marks an important moment for the CFML and BoxLang community not just because of what’s on the agenda, but because of what it represents: 20 years of Ortus Solutions helping teams move forward, modernize, and build with confidence.

Victor Campos
Victor Campos
January 21, 2026